home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000062_news@columbia.edu _Thu Oct 5 16:39:11 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id QAA19056
for <kermit.misc@cpunix.cc.columbia.edu>; Thu, 5 Oct 2000 16:39:10 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id QAA23971
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 5 Oct 2000 16:39:10 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id QAA23432
for kermit.misc@watsun.cc.columbia.edu; Thu, 5 Oct 2000 16:20:28 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: No Carrier
Date: 5 Oct 2000 20:20:27 GMT
Organization: Columbia University
Message-ID: <8rinqb$ms6$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <rg5D5.6722$Ly1.76783@news5.giganews.com>,
Steve <steve@baus-systems.com> wrote:
: What I am looking for is a way for the server PC that is sitting in K95
: SERVER mode to not drop the phone line, which is causing a no carrier on the
: DOS client, but exit all the way out of K95 when it receives the FIN from
: the DOS client. This will allow the server PC to process the file before it
: receives (or sends) additional files to the same client on the same
: communications session..
:
Whatever you want to do can be done. Just remember that while K95 is in
server mode, it is controlled by the client. When the client tells it to
FINISH, control returns back to the K95 command stream, whatever it happens
to be (your command file in this case). At that point, your command file can
do whatever you want it to do -- process the file and return to server mode,
or anything else. But if it goes back and forth between server mode and
local processing in a loop, the client needs some way to break the loop. One
way to do this is to have them give a BYE command when finished, instead of
FINISH.
Lots of other designs are possible that might be more appropriate. Perhaps
if you state the actual requirements of your application, we could suggest
a clean, safe approach.
- Frank